<text><span class="style21">yperTalk Programmers</span><span class="style1">You can use the external commands and fonts in this stack in your own stacks using the HyperTalk statement: start using stack "Colour Text Stack"Alternatively you may copy the resources from this stack into your own using a resource copying stack or ResEdit. Remember if you distribute stacks using this package you must include a copy of the license & copyright notice, see the license for details.The syntax of the </span><span class="style12">ColourText[RGB]</span><span class="style1"> XCFNs are: ColourText[RGB](</span><span class="style12">card</span><span class="style1">, </span><span class="style12">field id</span><span class="style1">, </span><span class="style12">scroll</span><span class="style1">, </span><span class="style12">wide</span><span class="style1">, </span><span class="style12">table</span><span class="style1">, </span><span class="style12">window</span><span class="style1">[, </span><span class="style12">visible</span><span class="style1">])where:card A boolean flag, true if colouring a card field.field id The id of the field to be coloured.scroll True for scrolling fields.wide True for fields with wide margins.table Name of the colour table to use.window Name for the window.visible Initial visibility of the window, true means visible. If omitted true is assumed.Return value Returns true if succesful.To ease the use of the XFCNs two function handlers are provided in the stack script: function Colourize[RGB](</span><span class="style12">field spec</span><span class="style1">, </span><span class="style12">table</span><span class="style1">, </span><span class="style12">window</span><span class="style1">)where:</span><span class="style12">field spec</span><span class="style1"> Name of field to colourize </span><span class="style12">as a string</span><span class="style1">, e.g. "cd fld fred".</span><span class="style12">table</span><span class="style1">, </span><span class="style12">window</span><span class="style1"> As above.The following externals are also in this stack for use by the </span><span class="style12">Colour Table Maker</span><span class="style1"> stack. BuildNPct </span><span class="style12">function</span><span class="style1">[,</span><span class="style12">arguments</span><span class="style1">]This XCMD is used to construct and save colour tables. You do not need to know how this works as the </span><span class="style12">Colour Table Maker</span><span class="style1"> stack is provided so you can build tables. If you wish to know how to use it read the scripts! ColourPicker(</span><span class="style12">prompt</span><span class="style1">[,</span><span class="style12">red</span><span class="style1">,</span><span class="style12">green</span><span class="style1">,</span><span class="style12">blue</span><span class="style1">])This XFCN displays a standard Colour Picker dialog. The dialog is automatically positioned in the best location (Apple's not my “best location”, so don't blame me if you think its a silly place on your Mac). An RGB value may optionally be supplied to use as the starting colour, if omitted white is used. The return value is a RGB value (3 numeric items).</span><span class="style21">Font Programmers</span><span class="style1">The fonts in this stack are duplicated in the font file “Colour Text Fonts”. The fonts in this stack & the suitcase share their NFNT's to save space, if you copy them this sharing will be lost unless you take care to preserve it. As the suitcase shares NFNTs you cannot open it with System 7, I see this as a bug in System 7 – it might of course be a feature :-( You can remove the fonts from this stack if you wish using ResEdit or Font/DA Mover – “option open” in the latter. You can copy the fonts into your system if you don't have SuitCase II etc. using Font/DA Mover, System 7.0.1 will </span><span class="style21">not</span><span class="style1"> open the suitcase.</span><span class="style21">Application Programmers</span><span class="style1">You may used the WDEF used by </span><span class="style12">ColourText[RGB]</span><span class="style1"> in your own programs if you wish, subject of course to the license conditions of this package. The WDEF has ID 528 and draws a white rectangular borderless window. All mouse clicks are reported as </span><span class="style12">inContent</span><span class="style1">.</span></text>
</content>
<name></name>
<script></script>
</card>
card_5954.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpgo to stack "Colour Table Maker"end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>3</id>
<text>Page 9 of 10</text>
</content>
<content>
<layer>background</layer>
<id>9</id>
<text>Colour Tables</text>
</content>
<content>
<layer>background</layer>
<id>2</id>
<text><span class="style1">he colour tables used to map font names or </span><span class="style12">Colour Switcher</span><span class="style1"> characters to colours are stored as </span><span class="style12">resources</span><span class="style1">. The stack </span><span class="style12">Colour Table Maker</span><span class="style1"> is provided which enables the construction and deletion of colour tables.</span></text>
</content>
<name></name>
<script></script>
</card>
card_4074.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">he </span><span class="style21">big</span><span class="style1"> advantage of using windows for colour text is that they are a standard HyperCard facility and should therefore not break in future versions of HyperCard. There are some disadvantages. First you'll notice a slight delay when switching to a card with colour in this stack before the colour appears, this is due to the time taken to construct the window and (very) carefully draw it over the top of the existing field to reduce any update flicker. Second, and more important, windows are treated as independant entities by HyperCard, they do not </span><span class="style12">belong</span><span class="style1"> to any particulart card window. This translates to; move the card window and the colour text windows stay behind… This is why the title bar has been hidden on this stack, so you cannot move the card window and leave the colour behind. This problem can however be scripted around by writing handlers for the standard HyperCard </span><span class="style12">moveWindow</span><span class="style1"> and </span><span class="style12">sizeWindow</span><span class="style1"> messages – we leave this as an exercise.</span></text>
</content>
<name></name>
<script></script>
</card>
card_3640.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">here are three primary ways to add colour to HyperCard displays:1) “The Internal Parasite”. This method digs into HyperCard's internals and adds in colour buffering and screen drawing. Depending on how deep the added colouring code is buried HyperCard this allows the background and/or HC objects (buttons, fields) to be coloured. The disadvantages are that it uses a lot of memory for the colour buffers (which typically have to be card sized) and will probably break when a new version of HyperCard is released as the internals will change. The advantage of this method is colour which is cleanly incorporated into the displayed image. This is the method used by Colorize HC and, I believe, HyperTint.2) “The Surface Rash”. This method simply draws colour images directly into HyperCard's window (or the same area of display) </span><span class="style12">without</span><span class="style1"> HyperCard's knowledge. Unfortunately if HyperCard updates the card image, as it does not know the colour image is there, it just draws over it – this erases the coloured image (completely or partially depending on where HyperCard draws). This is one of the methods used by the QuickTime XCMDs from Apple/Claris.3) “External Windows/Palettes”. This is the only method which HyperCard directly supports; thus it should work with future versions, unlike (1), and won't be accidentally erased, unlike (2). It works by drawing in a different window to that used by the card image. Such windows may be moved, hidden, closed etc. using standard HyperTalk commands. They are created by special external commands, the navigator palette and tear-off tool menu are examples which are part of the standard HyperCard release. The standard Picture external and the QuickTime externals use this method to display colour. The Pictoid Package and Colour Text also use this method. In the case of Pictoids the windows may be any shape, contain pictures/movies, have no standard window-like frame, and act like buttons. Colour Text uses special borderless windows which are drawn directly over the field being coloured and are hence (almost) invisible.</span></text>
</content>
<name></name>
<script></script>
</card>
card_4178.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput me into logoif logo contains "(1)" thenset the textFont of cd fld "Demo" to "Colour Switcher"put "(2) Colour field" into meelse if logo contains "(2)" thenget Colourize("cd fld Demo", "Example Font Colours", "Colour")put "(3) Reset demo" into meelseresetDemoend ifend mouseUpon resetDemoif there is a window "Colour" then close window "Colour"set the scroll of cd fld "Demo" to 0set the textFont of cd fld "Demo" to "Colour Marker"put "(1) Change base font to Colour Switcher" into meend resetDemo</script>
</part>
<content>
<layer>background</layer>
<id>3</id>
<text>Page 6 of 10</text>
</content>
<content>
<layer>background</layer>
<id>9</id>
<text>Method 2 (cont)</text>
</content>
<content>
<layer>background</layer>
<id>2</id>
<text><span class="style1">ethod 2 may seem a lot better than method 1; </span><span class="style12">any</span><span class="style1"> font can be coloured </span><span class="style12">any</span><span class="style1"> of the available colours by just inserting the appropriate characters from </span><span class="style12">Colour Switcher</span><span class="style1"> – no need to use different fonts for different colours. However, things are never that easy! As method 2 relies on switching characters, if the switching characters are not actually printed, i.e. the are scrolled offscreen or hidden under something else, then the colour will not switch, or will switch in interesting ways :-(. The example below demonstrates the problem:</span></text>
</content>
<content>
<layer>card</layer>
<id>5</id>
<text><span class="style83"></span><span class="style26">Method 2</span><span class="style83">!</span><span class="style26"> may seem a lot better than method 1; </span><span class="style82">any</span><span class="style26"> font can be coloured </span><span class="style82">any</span><span class="style26"> of the available colours by just inserting the appropriate characters from </span><span class="style82">Colour Switcher</span><span class="style26"> – no need to use different fonts for different colours. </span><span class="style83">"</span><span class="style26">However, things are never that easy!</span><span class="style83">!</span><span class="style26"> As method 2 relies on switching characters, if the switching characters are not actually printed, i.e. the are scrolled offscreen or hidden under something else, then the colour will not switch, or will switch in interesting ways </span><span class="style83">#</span><span class="style26">:-(</span><span class="style83">!</span><span class="style26">.</span></text>
</content>
<content>
<layer>card</layer>
<id>7</id>
<text>(1) Change base font to Colour Switcher</text>
</content>
<name></name>
<script>on openCardsend resetDemo to cd fld "demoButton"pass openCardend openCardon closeCardsend resetDemo to cd fld "demoButton"pass closeCardend closeCard</script>
</card>
card_2516.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">he second method provided to colour text is the font </span><span class="style12">Colour Switcher</span><span class="style1">. When </span><span class="style12">ColourText[RGB]</span><span class="style1"> prints a character using the </span><span class="style12">Colour Switcher</span><span class="style1"> it first switches the current foreground and background colours according to the value of the character – the character ‘!’ (ASCII 33) sets the colours to black & white, subsequent characters ‘"’, ‘#’, ‘$’, etc. (ASCII 34, 35, 36, etc.) select the colours in the 1st, 2nd, 3rd, etc. entries in the colour table; the three character font name field is ignored. All characters in the </span><span class="style12">Colour Switcher</span><span class="style1"> font are invisible so that you may switch colours in your text without any visible control characters.Invisible characters are rather hard to type (!), so to making using </span><span class="style12">Colour Switcher</span><span class="style1"> possible a second font </span><span class="style12">Colour Marker</span><span class="style1"> is included, this font contains the characters: </span><span class="style81">!</span><span class="style1">, </span><span class="style81">"</span><span class="style1">, </span><span class="style81">#</span><span class="style1">, </span><span class="style81">$</span><span class="style1">, etc. (up to </span><span class="style81">?</span><span class="style1"> at present). You may type in your text using the </span><span class="style12">Colour Marker</span><span class="style1"> font to show the colours and then change all text in </span><span class="style12">Colour Marker</span><span class="style1"> to </span><span class="style12">Colour Switcher</span><span class="style1">.</span><span class="style21">Hint</span><span class="style1">: To make switching between </span><span class="style12">Colour Marker</span><span class="style1"> and </span><span class="style12">Colour Switcher</span><span class="style1"> easy use the following steps:1) Set the base font of the field to </span><span class="style12">Colour Marker</span><span class="style1"> using the </span><span class="style31">Field Info…</span><span class="style1"> dialog.2) Using the </span><span class="style31">Font</span><span class="style1"> menu change the font of typed text to the one you wish to use.3) When you wish to change text colour use the </span><span class="style31">Font</span><span class="style1"> menu to select the </span><span class="style12">Colour Marker</span><span class="style1"> font.4) When finished entering the text use the </span><span class="style31">Field Info…</span><span class="style1"> dialog to change the base font to </span><span class="style12">Colour Switcher</span><span class="style1"> – all characters in </span><span class="style12">Colour Marker</span><span class="style1"> will change face (and become invisible).5) If you wish to edit the field use the </span><span class="style31">Field Info…</span><span class="style1"> dialog to change the base font back to </span><span class="style12">Colour Marker</span><span class="style1">.</span></text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<highlight> <true /> </highlight>
</content>
<name></name>
<script></script>
</card>
card_4611.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">he disadvantages of using the text font to indicate colour are obvious, it relies on font names being unique in their first three letters and coloured text must be in a different font to black on white text. Both these disadvantages can be addressed by constructing special fonts for colouring, these can be based on existing fonts with just the names changed.</span><span class="style21">Example</span><span class="style1">This stack contains the following fonts, all just renamed versions of Monaco: </span><span class="style56">%01Monaco</span><span class="style80">, </span><span class="style57">%02Monaco</span><span class="style80">, </span><span class="style58">%03Monaco</span><span class="style80">, </span><span class="style59">%04Monaco</span><span class="style80">, </span><span class="style60">%05Monaco</span><span class="style80">, </span><span class="style61">%06Monaco</span><span class="style80">, </span><span class="style62">%07Monaco</span><span class="style80">, </span><span class="style63">%08Monaco</span><span class="style80">, </span><span class="style64">%09Monaco</span><span class="style80">, </span><span class="style65">%10Monaco</span><span class="style80">, </span><span class="style66">%11Monaco</span><span class="style80">, </span><span class="style67">%12Monaco</span><span class="style80">, </span><span class="style68">%13Monaco</span><span class="style80">, </span><span class="style69">%14Monaco</span><span class="style80">, </span><span class="style70">%15Monaco</span><span class="style80">, </span><span class="style71">%16Monaco</span><span class="style80">, </span><span class="style72">%17Monaco</span><span class="style80">, </span><span class="style73">%18Monaco</span><span class="style80">, </span><span class="style74">%19Monaco</span><span class="style80">, </span><span class="style75">%20Monaco</span><span class="style80">, </span><span class="style76">%21Monaco</span><span class="style80">, </span><span class="style77">%22Monaco</span><span class="style80">, </span><span class="style78">%23Monaco</span><span class="style1"> and </span><span class="style79">%24Monaco</span><span class="style1">These variants of Monaco have been named so that name clashes with existing fonts are unlikely. The use of the '%' as the first character stops the fonts from appearing in standard font menus, this is a standard Macintosh feature.</span><span class="style21">Note for ResEdit and Font Hackers</span><span class="style1">Special fonts for text colouring take up space but need not take up a lot if they are carefully constructed. All 24 variants of Monaco in this stack share the same bitmap resources (NFNTs), i.e. there are 24 font descriptions (FONDs) but only two bitmaps (9 & 12 point NFNTs).</span></text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<highlight> <true /> </highlight>
</content>
<name></name>
<script>on openWindowsget Colourize("bg fld Text", "TextColours", "Colour")end openWindowson closeCardif there is a window "Colour" thenclose window "Colour"end ifend closeCard</script>
</card>
card_4374.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">he colour of text can be specified using two methods. The first method determines the colour from the text font and the colour table. Each colour table entry is a triple of the form:<first three letters of font name>,<text colour>,<background colour>When ColourText[RGB] draws text on the screen it first checks whether the first three letters of the text font match an entry in the colour table and if so changes the text & background colours. This method will work well in any style of field.</span><span class="style21">Example</span><span class="style1">This field has been coloured using the call:     get Colourize("bg fld Text", "Example Font Colouring", "Demo")The colour table “Example Font Colouring” colours </span><span class="style29">New York</span><span class="style1"> font red, </span><span class="style13">Monaco</span><span class="style1"> green, </span><span class="style30">Geneva</span><span class="style1"> yellow on blue and </span><span class="style31">Chicago</span><span class="style1"> cyan (these fonts have been picked as they're standard on Macintoshes, others can be used). You will notice that as you scroll this field the coloured text scrolls correctly, and if you're using System 7 you will also notice that the scroll bar is coloured.</span></text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<highlight> <true /> </highlight>
</content>
<name></name>
<script>on openWindowsget Colourize("bg fld Text", "Example Font Colours", "Colour")end openWindowson closeCardif there is a window "Colour" thenclose window "Colour"end ifend closeCard</script>
</card>
card_2150.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">he </span><span class="style12">ColourText </span><span class="style1">and </span><span class="style12">ColourTextRGB</span><span class="style1"> XFCNs colour the text in a field using either the original 8 QuickDraw colours (ColourText) or Colour QuickDraw RGB colours (ColourTextRGB). To make the use of these XFCNs simpler two function handlers, </span><span class="style12">Colourize</span><span class="style1"> and </span><span class="style12">ColourizeRGB</span><span class="style1">, are provided in the stack script to call the XFCNs themselves. The syntax of these functions is:Colourize[RGB]("<field specification>", "<colour table>", "window name")Where: the </span><span class="style12">field specification</span><span class="style1"> is a string identifying the field to colour, e.g. "cd fld id 1"; the </span><span class="style12">colour table</span><span class="style1"> is the name of a colour table resource used to determine text colour; and </span><span class="style12">window name</span><span class="style1"> is the name to use for the window ColourText[RGB] uses to draw the colour text into (the use of windows will be explained later).</span></text>
</content>
<name></name>
<script></script>
</card>
card_2867.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">yperCard 2.1 does not directly support colour, though a future version from Claris is rumored to. There are however a number of existing ways of adding colour to stacks, primary among which are:• The Picture XCMDThis XCMD comes with HyperCard and will display colour pictures in standard Macintosh windows, either in the card or palette window layer of HyperCard. If you have Wild Magic installed then Picture will also display QuickTime movies™.• The QuickTime™ Externals from Apple/ClarisEither as part of the QuickTime™ package from Apple, or as part of the latest release of HyperCard from Claris, a number of externals are available which will display QuickTime™ movies and compressed pictures. These externals will use standard Macintosh windows or draw directly into the card window; the disadvantage of the latter approach being that HyperCard does not know about the drawing and may erase it.• Colorize HyperCardThis is a FreeWare stack from BungDubba (?sp) which contains externals which can colour any part of a card. This stack is very powerful but unfortunately due to the multiple screen buffering which must be used a large amount of memory is consumed when using it. You should be able to ftp it from your local archive site. (BungDubba is rumored to really be the Claris HC team…)• The Pictoid PackageThis is a “free for non-commercial use” package (license similar to Colour Text's) which support the display of colour pictures and QuickTime™ movies in any-shape windows. These windows need not have borders and may have scripts attached to them so that they behave like buttons, thus giving the illusion of any-shape coloured buttons in HyperCard. The package also contains a number of other utilities, including “Sticky Buttons” which can be embedded into scrolling text fields. You should be able to ftp this package from your local archive site. Disclaimer: This package was written by the same author as Colour Text, so I'm naturally biased!• HyperTintThis is a commercial package along the lines of Colorzie HyperCard described above. A demo version is available on archive sites.None of the above provide a simple, low memory usage, way of drawing coloured text in HyperCard fields. The Colour Text Package has been written to fill this gap.</span><span class="style21">Acknowledgement</span><span class="style1">The first version of this package was written for Doug Eernisse, University of Michigan, to enable various DNA strings to be displayed in colour for easy identification. Thanks go to him for getting me thinking, for testing the result, and giving useful feedback. If later in this stack you wonder why some of the supplied colour tables have 24 entries the answer is that 24 colours are required to colour the peptides & DNA in Doug's stack… If you'd like to use Doug's stack it is called “Aligner” and is available as “Aligner.hqx” by ftp to ftp.bio.indiana.edu in subdirectory molbio/mac.</span></text>
</content>
<name></name>
<script></script>
</card>
card_5541.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUplock screenset lockMessages to truesend closeCard to this cdgo next cardsend openCard to this cdunlock screen with visual effect wipe leftopenWindowsset lockMessages to falseend mouseUp</script>
</part>
<part>
<id>9</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>0</left>
<top>188</top>
<right>26</right>
<bottom>212</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>21700</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Home</name>
<script>on mouseUpgo homeend mouseUp</script>
</part>
<part>
<id>14</id>
<type>field</type>
<visible> <true /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>14</left>
<top>46</top>
<right>403</right>
<bottom>187</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Times</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>Copyright</name>
<script></script>
</part>
<part>
<id>15</id>
<type>field</type>
<visible> <true /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>39</left>
<top>7</top>
<right>376</right>
<bottom>43</bottom>
</rect>
<style>shadow</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Colour Switcher</font>
<textSize>24</textSize>
<textStyle>italic</textStyle>
<textStyle>bold</textStyle>
<textHeight>32</textHeight>
<name>Title</name>
<script>on mouseDownif the optionKey is downthenset the visible of bg btn "Lock" to not the visible of bg btn "Lock"end ifend mouseDown</script>
</part>
<part>
<id>16</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>303</left>
<top>186</top>
<right>403</right>
<bottom>203</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Times</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Version History</name>
<script>on mouseUpif the visible of cd fld "History" thensend hideField to cd fld "History"elsesend showField to cd fld "History"end ifend mouseUp</script>
</part>
<part>
<id>17</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>14</left>
<top>46</top>
<right>403</right>
<bottom>187</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Times</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>History</name>
<script>on mouseUphideFieldend mouseUpon showFieldif not the visible of me thenlock screenshow meset the name of cd btn id 16 to "Introduction"unlock screen with visual effect wipe leftend ifend showFieldon hideFieldif the visible of me thenlock screenhide meset the name of cd btn id 16 to "Version History"unlock screen with visual effect wipe rightend ifend hideField</script>
</part>
<content>
<layer>background</layer>
<id>6</id>
<text>Dr N Perry, Department of Computer Sicence, Massey University,Palmerston North, New Zealand. Email: N.Perry@massey.ac.nz</text>
<text>Version 1.0: July 92    Initial Release.Version 1.1: Sept 92    The invisible colour text windoid was being created at the front of all    other windoids instead of behind them. This meant that if another    windoid (e.g. message box) was over the field being coloured then a    picture of the windoid was superimposed over the colour text. Thanks    to Matt Neuberg for reporting this.</text>
</content>
<name>Intro</name>
<script>on openCardset the scroll of cd fld "Copyright" to 0set the scroll of cd fld "History" to 0end openCardon openWindowsget Colourize("cd fld Title","TextColours",Colour)end openWindowson closeCardsend hideField to cd fld "History"if there is a window "Colour" thenclose window "Colour"end ifset the scroll of cd fld "Copyright" to 0end closeCardon arrowKey whichif which is "Right" thensend mouseUp to btn "Next"elseif which is not "Left" thenpass arrowKeyend ifend ifend arrowKey</script>